[modsecurity] Generate processor tags and normalize error handler #15563
Conversation
taylor-swanson
added
enhancement
|
/test |
- Generate tags for processors missing tags - Normalize the pipeline error handler
taylor-swanson
force-pushed
the
enhance/tag-modsecurity
branch
from
908cfcf to
5b47582
Compare
💚 Build Succeeded
History
|
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
| patterns: | ||
| - "%{NOTSPACE:http.request.method} %{URIPATHPARAM:url.original}(?: HTTP/%{NUMBER:http.version})" | ||
| - rename: | ||
| tag: rename_json_transaction_request_headers_host_to_json_transaction_request_headers_Host_50a00924 |
There was a problem hiding this comment.
Just curious.. Hope there is no limitation on the tag character length?
There was a problem hiding this comment.
That's a good question... I don't think there is? Not aware of anything in elasticsearch itself (aside from maybe the default limit we put on fields, I can't recall what it was but I think it's 1024 or higher). I don't think BigQuery will impose any limits either. Data types should be variable length, and don't think we impose limits there.
There was a problem hiding this comment.
@haetamoudi, are you aware of limits in BigQuery or other places?
There was a problem hiding this comment.
should be fine. Here is a valid tag name that is already present in stats tables in bigquery
|
Package modsecurity - 1.21.2 containing this change is available at https://epr.elastic.co/package/modsecurity/1.21.2/ |
4 participants
Proposed commit message
Checklist
changelog.ymlfile.- [ ] I have verified that any added dashboard complies with Kibana's Dashboard good practices